When you develop Knowledge Management and Collaboration (KMC), you
edit java files in the SAP NetWeaver Developer Studio and test and debug
them in the SAP Enterprise Portal. To set up your development
environment, you need to perform the following steps:
- Install a local JDK.
- Install a local SAP NetWeaver Developer Studio
For instructions on how to perform the installation, see service.sap.com/instguidesNW04
->Installation -> Dev Env -> Installation Guide -> SAP
NetWeaverDeveloper Studio
- Make sure a remote SAP Enterprise Portal with Knowledge
Management and Collaboration is available for testing.
- Set up a connection to the remote portal as described in the next
section.
Useful Details
Establishing a Connection to the Remote Portal
To enable the deployment of KMC PAR files from the SAP Developer
Studio to the test portal, you need to set up a connection to the
portal. To do this, open the Developer Studio and choose Window -> Preferences -> SAP Enterprise Portal and then
enter the required connection data.
Note that for Login you specify a portal user that has the
authorization for deployment of PAR files. This can, for example, be a
user with the system_admin_role
Keep in mind the following restrictions, for testing on a remote
portal:
- Only one person can debug and trace. Simultaneous debugging is
not possible.
- After deployment, you always need to restart the SAP J2EE Engine
(or at least the portal service) to activate the deployed components.
Therefore, if several developers are sharing a test portal, it is
essential to coordinate deployment.
- If several developers write code locally and then deploy it on a
shared remote portal, unexpected errors may occur. This happens when the
version of jar files that is used to compile locally is incompatible
with the version that is used at runtime on the remote portal.
Underlying dependencies between the code developed by different
developers, which are not visible in the local environment, cause the
errors. Keep in mind that local jar files must always be kept in sync
with the jar files on the remote portal.
The normal development cycle consists of setting up a development
project, coding in Eclipse, deploying PAR files into the portal and then
debugging and testing in the portal. When you start development, two
approaches are possible. You can:
- Use Knowledge Management wizards
These are integrated in the developer Studio and give support for
developing the following components:
- Repository managers and submanagers
- Repository services
- Global services
- Filters
- Scheduler tasks
For more information, see Setting Up a Project with Wizards.
- Set up projects manually
If no wizards are available for your tasks, you need to set up a
project manually. For more information, see
Setting Up a Project Manually.